When playin with Direct3D driver, i got game speed reduced, although i still have 70 Frames per Second. When i move arround a dynamic (or static) light, the game seems to run slowly, but the frames per second does not went down. If i turn on FRAPS, and start to record a game video, the game returns to it's normal speed. This does not occur when usin OpenGL Driver. I will try to record a film of the game with my digital camera, so you can see the effect. I will upload the video a bit later. [EDIT] When using version 2.18

Hmm... I somehow thing this connects to the weapon speed reduction I noticed.

[quote="Edward850":2v7e4gum]Hmm... I somehow thing this connects to the weapon speed reduction I noticed. Not only the weapons, the whole game seems to be running at 10% of normal game speed, although i have a nice FPS rate. I have recorded a video with my digital camera, but i need now a program to convert from .MOV to .AVI or something else...

There might be a problem when rendering something, my guess is that skybox rendering might be the problem. AFAIK there's no way to fix the weapons state duration, since it's tight to the FPS rendering in game. As for video format conversions, I have tested this site and it works fine: [url:duadw48w]http://online.movavi.com/?mode=file

[quote="Firebrand":1lz30jo6]There might be a problem when rendering something, my guess is that skybox rendering might be the problem. AFAIK there's no way to fix the weapons state duration, since it's tight to the FPS rendering in game. As for video format conversions, I have tested this site and it works fine: [url:1lz30jo6]http://online.movavi.com/?mode=file I got that issue even playing plain Doom2.wad. I will try that webpage and show you all the video.

Fixed.

Can't... wait... for... update... What was wrong anyway? (c++ wise, I'm learning C++ and I need to learn from other peoples mistakes (not to sound rude or anything)).

By default Direct3D switches FPU to single precision which messes up floating point calculations using doubles because precision is lost. So you have to tell Direct3D to preserve FPU state.